Intelligent communications point platform

ABSTRACT

A system and method for host signaling processing that allows multiple SS7 applications to have visibility to the SS7 network traffic and the ability to control the SS7 network traffic. The applications residing on the platform have visibility to the SS7 traffic flowing through the Intelligent Communications Point (ICP) Platform, ability to control and modify the traffic and the ability to inject new SS7 traffic onto the SS7 links. The ICP platform will provide basic services that applications can use including Logging Data, Process Events, Inter Process Communication Services, and an interface to the Intelligent Communications Manager which provides a graphical user interface to manage the ICP. In addition to these services, the ICP Platform will provide basic traffic metering and measurement, bookkeeping statistics, and a failsafe mechanism for the SS7 links.

RELATED PATENT APPLICATIONS

This application relates to the following United States PatentApplication, incorporates them by reference in their entirety and isassigned to the assignee of the present invention:

Filing Serial No.: Date: Inventors: Title: 09/536,958 3/28/2000 Ashdownet al. New and Improved System and Method for Data Traffic Redirection09/537,016 3/28/2000 Ashdown et al. System and Method for a Local NumberPortability Cache 09/391,295 09/07/99 Ashdown et al. SS7 Firewall System

FIELD OF THE INVENTION

This invention relates generally to the Common Channel Signaling System7 (SS7) network technology and, more particularly, to a host signalingprocessing platform that allows multiple SS7 applications to havevisibility to SS7 network traffic while also having the ability tocontrol SS7 network traffic.

BACKGROUND

The SS7 network is the backbone of the world's telecommunicationsnetworks. Service providers across the globe rely on the SS7 network toimplement setup, routing, and control of a call, as well as to provideresidential, business, and government customers advanced services suchas 800 and 900 calling, caller ID, local number portability, and callingcard verification. Without the SS7 network, the world'stelecommunications networks would not function as we know it today.

SS7 is a means to exchange information between nodes (switching systems,network data bases, or operator service systems) in a signaling networkwhere messages are not carried over voice circuits but instead utilizeseparate links to convey the signaling information. Traditionalinteroffice signaling uses in-band signals to convey signalinginformation. Communications on an SS7 network falls into two distinctcategories, command and control signals and network-traffic. However,general voice traffic is carried in-band on voice channels. Command andcontrol signals are carried out-of-band and are used to manage thenetwork traffic. The SS7 network is comprised of a number of differenttypes of signaling nodes, including Service Switching Points (SSPs),Signaling Transfer Points (STPs), and Service Control Points (SCPs).SSPs originate, manage, and terminate calls. SCPs act as centralizeddatabases that validate, authorize and answer service requests fromSSPs, such as how to route an 800 number call. STPs route SS7 messagesbetween SSPs, SCPs, and other STPs.

The SS7 Network uses six types of signaling data links to connect thevarious nodes. The link specific functions and associated types of nodeswith which they interact are described as follows:

A LINKS STP-SSP SAME NETWORK STP-SCP SAME NETWORK B LINKS STP-STP SAMEHIERARCHY LEVELS C LINKS STP-STP MATED PAIRS D LINKS STP-STP DIFFERENTHIERARCHY LEVELS E LINKS STP-STP DIFFERENT NETWORKS/STP STP-SCPDIFFERENT NETWORKS/STP F LINKS SSP-SSP SAME NETWORK

A LINKS (Access Links) carry the primary traffic of the network in theSS7 configuration. B-LINKS (Bridge Links) interconnect STP mated pairsto other mated STP pairs of the same hierarchical level. C LINKS (CrossLinks) interconnect STP mated pairs together and are used primarily foradministrative traffic. They can also carry message traffic if needed. DLINKS (Diagonal Links) interconnect STPs of different hierarchicallevels which are primary and secondary signaling transfer points (i.e.regional STP to local STP). E LINKS (Extended Links) connect a switchingoffice [SSP or Signaling Point (SP)] to an STP other than its home STP.F LINKS (Fully Associated Links) connect SSPs to other SSPs and are usedfor associated signaling between the two. These SSPs must be adjacentnodes.

However, never has a system and method been created that can havevisibility into the SS7 network, but not interrupt it, and yet itprovides the ability to build SS7 based applications efficiently andseamlessly.

SUMMARY OF THE INVENTION

The present invention attempts to solve these problems. Accordingly, thepresent invention describes a system and method for providing a basicset of core services that will allow multiple SS7 based applications tobe developed and deployed. The present invention includes an IntelligentCommunication Point (ICP) Platform which is managed by a Graphical UserInterface (QUI) known as the Intelligent Communication Manager (ICM).Moreover, multiple ICP Platforms can be managed by the ICM. The ICP canreside on a computer that contains one or more Central Processing Units(CPUs) and supports the SS7 interface. A real-time operating system isdeployed on the computer and provides, not only high availabilitysupport, but also supports the hot swap standards.

These and other objectives and features of the invention encompass acomprehensive system for providing an active SS7 platform for buildingSS7 based applications.

Therefore, in accordance with the previous summary, objects, featuresand advantages of the present invention will become apparent to oneskilled in the art from the subsequent description and the appendedclaims taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of signaling end point connections in an SS7network;

FIG. 2 is an overview of the ICP Platform;

FIG. 3 is a block diagram of SS7 network link routing;

FIG. 4 is a functional diagram of the ICP Platform;

FIG. 5 is a block diagram of the configuration data flow;

FIG. 6 is a block diagram of the provisioning data flow; and

FIG. 7 is a block diagram of the processing data flow.

DETAILED DESCRIPTION

First a brief overview of the present invention's preferred embodimentwill be described and then will be described in greater detail inreference to the figures. To start with, the ICP Platform is not an endpoint in the network, but rather an invisible node that sits in front ofa Signaling End Point (SEP), which may be, for example, a SignalingTransfer Point (STP), Service Switching Point (SSP), or Service ControlPoint (SCP). All SS7 links are routed into the ICP and are then routedout to the SS7 network. In addition, the ICP Platform design can bebroken down into five parts; SS7 links cards and SS7 stack, interface tothe ICM, platform core services, software and hardware control/status,and the application region.

SS7 Link Cards and SS7 Stack

The ICP Platform contains multiple T1/E1 link cards. All SS7 links froman SSP are routed into the ICP and then out to the SS7 network. Eachlink card supports multiple links and processes Message Transfer Part(MTP) layers 1 and 2, while the CPU host card supports the ICP coreservices, applications, and MTP layer 3. MTP1 defines the physical,electrical, and functional characteristics for the digital signalinglink. MTP2 ensures accurate end-to-end transmission of a message acrossa signaling link. In addition, MTP2 implements flow control, messagesequence validation, and error checking. When an error occurs on asignaling link, the message (or set of messages) is retransmitted.Moreover, MTP2, which resides on the link cards, has a failsafe mode.When MTP3 fails, MTP2 will automatically route traffic between the SEPand the SS7 network.

MTP3 provides message routing between signaling points in the SS7Network and routes traffic away from failed links and signaling points.In addition, MTP3 controls traffic when congestion occurs. In the ICPPlatform, two links are required to achieve the usage of one normallink. The ICP sits between an SSP and SS7 network and literally breaksthe link into two links. These two links are considered to be one linkpair. All SS7 traffic coming in one link will be routed out of the ICPthrough the other link of the link pair (FIG. 3). If the ICP fails dueto hardware or software failures, these link pairs close allowing theSS7 traffic to pass through the ICP as if the ICP was not in thenetwork. The link pairs can also be manually closed while still allowingthe ICP to have visibility to the SS7 traffic flowing through the linkpairs. In addition, link cards route non-SS7 traffic on open DS-0 datalines directly to the other port without going through the ICP.

Interface to the Intelligent Communication Manager (ICM)

The ICP Platform is managed by the ICM. The ICP interface is the bridgefor communications between the ICP and the ICM. Through this interfacesoftware, the ICM user can gain access to the ICP core services andapplication software. The interface allows the user to bring the ICPinto service, bring up and down application software, retrieve ICP coreservice data such as logs and events, retrieve application specificdata, and configure/status the ICP hardware/software.

Platform Core Services

The ICP Platform provides a set of core services for the developers ofthe applications to use when designing the application, includingLogging Data, Process Events, Peg Counting, and the SS7 messageinterface (FIG. 3). Logging Data services allow the applications tocollect data which can be passed to the ICM for display to the customer.Process Event service is a method in which alarms can be raised toinform customers of an event that may or may not be critical. Each eventis marked with a severity level which indicates to the user whether theevent needs attention or not. Peg Counting services are tied in with thetraffic metering and measurement (TMM) and bookkeeping processes. Alongwith the core set of peg counts, applications will also have their ownsets of peg counts that can be collected and displayed on the ICMthrough the TMM graphical user interface (GUI). The SS7 messageinterface service allows applications to have access to SS7 trafficflowing through the ICP. The ICP processes all SS7 traffic according torules. These rules define the actions as to how the SS7 message is goingto be processed. Customers can implement rules that will act as a SS7Firewall to protect the SEP (refer to the pending SS7 Firewall Systempatent, dated Sep. 7, 1999). Applications can receive SS7 traffic byimplementing application rules that pass the message from the stack upthrough to the application, or can send out SS7 messages through an ICPSS7 API (Application Programming. Interface).

Software and Hardware Control/Status

Software on the ICP is managed by the platform manager (FIG. 4). Theplatform manager is responsible for starting core services andapplications. In the event of a software failure, the platform managerwill attempt to restart the failed software along with raising events tothe ICM and closing the link pairs so that SS7 traffic is not disrupted.The manager software will send status of the software and overall ICPhealth to the ICM through the ICP interface software. The hardware andthe SS7 stack configuration are handled by System Management Software.Through the use of a configuration file stored on the ICM, the SystemManagement Software programs the hardware interfaces such as the SS7link cards and configures the SS7 stack software. Status of the hardwareand state of the paired links (open or closed) are sent to the ICMthrough the ICP interface software.

Application Region

The heart of the ICP Platform is its ability to host any number ofdifferent SS7 applications (FIG. 3). Local Number Portability Cache(LNPC) is just one example of an application that could be developed forthe ICP Platform. Through the use of the ICP core services, developerscan design applications that can interact with the SS7 network.Application Programming Interfaces (APIs) are available to theapplication designers. These APIs allow the designers access to the coreservices and aid in the development process.

Now referring to the figures, FIG. 1 represents the end pointconnections in a SS7 network. Reference numeral 10 designates asignaling end point (SEP) which may be, for example, a SignalingTransfer Point (STP), Service Switching Point (SSP) or Service ControlPoint (SCP) and reference numeral 12 designates signaling transferpoints (STPs). In a typical SS7 network, traffic flows on data links 14between STPs and SEPs.

FIG. 2 illustrates the placement of the ICP Platform 200 within the SS7network. The ICP Platform 200 is not an end point in the SS7 network butrather an invisible node that sits in front of an SEP 210/220, which maybe for example, an STP, SSP or an SCP. All SS7 data links 14 are routedinto the ICP Platform 200 and are then routed out to the SS7 network.The SS7 network includes redundant DS-1 or DS-0A links 14, which arehigh speed serial links.

ICP Platform 200 processing distribution is driven by the signalingprotocol stack as shown in FIG. 2. The MTP1/MPT2 230/240 layer has anumber of link cards (E1/T1). The MTP1/MTP2 230/240 layer is looselycoupled with the MTP3 250 layer allowing MTP1/MPT2 230/240 to reside onthe link cards and MTP3 250 to reside on the single board computer. MTP1230 defines the physical, electrical, and functional characteristics forthe digital signaling link. MTP2 240, which resides on the link cards,has a failsafe mode. When MTP3 250 fails, MTP2 240 will automaticallyroute traffic back down and out to the SEP. MTP2 240 ensures accurateend-to-end transmission of a message across a signaling link 14. Inaddition, MTP2 240 implements flow control, message sequence validation,and error checking.

The MTP3 250 layer can interface with multiple MTP2 240 processors onthe link cards through a compact Peripheral Component Interconnect(cPCI) bus. By modifying the MTP3 250 layer to disable messagediscrimination, all messages are allowed to be passed up to the ICPPlatform 200 for processing. The MTP3 250 layer can be easily modifiedby making appropriate changes in the SS7 protocol stack being used.

In addition, MTP3 250 manages the Message Signaling Unit (MSU)/Linkassociation and has end to end management message coordination. MTP3 250also provides message routing between signaling points 210/220 in theSS7 Network, and can route traffic away from failed links and signalingpoints. Moreover, MTP3 250 controls traffic when congestion occurs.

The Core Services 260 layer supports various support services andsignaling processes to distribute traffic upwards to the Applications270 layer and accept downward message routing requests. The CoreServices 260 layer contains various subsystems and processes withinthese subsystems that developers of applications can use when designingapplications.

The Applications 270 layer contains all the applications that areimplemented above the Core Services 260 layer. The Applications 270layer supports various applications that can monitor, modify, or createmessages. Each application can process its own set of messages, use itsown rules and can be independent of other applications in general. Inaddition, one or more of the application processes may be running at agiven time to load-share the work.

As shown in FIG. 3, a SS7 MTP3 MSU 300 addressed for a signaling point,e.g., 220, travels from a signaling point, e.g., 210, through, the ICPPlatform 200. The MSU 300 goes through a MTP1 port 230 and then travelsup the SS7 protocol stack through the MTP2 240 I/O card and MTP3 250stack. The MTP3 250 stack may reside on the CPU card, or on the I/Ocard. A heartbeat signal 310 is maintained between MTP2 240 and MTP3250. Loss of the heartbeat 310, indicating a failure of the CPU cards inthe MTP3 250 layer, results in a failsafe mode (closed mode). During afailsafe mode, message traffic is passed up only to MTP2 240 and is thenrouted back down and out. If the CPU is available, a copy of the MSU 300is passed to MTP3 250 for non-intrusive processing. During normaloperation (open mode), data is transmitted between MTP1/MTP2 230/240 andMTP3 250. The MSU 300 is then delivered to Core Services 260 whichcontains various subsystems and processes within these subsystems. Someof those subsystems and processes will described in detail below.

The Platform Control Subsystem (PCSS) 311 has data provisioningcapability and is also responsible for the management of all the othersubsystems. In particular it starts and stops all the other processes ina controlled manner. The Signaling Subsystem (SGSS) 312 routes anddistributes SS7 messages. This subsystem processes every message thatpasses through the ICP Platform 200. However, since Fill-in Signal Unit(FISU) messages do not pass up to the ICP platform 200, they are notprocessed by the SGSS 312. The Interface Subsystem (IFSS) 313 isresponsible for the external system interface. In addition, the ICPSystem has the capability to interface with multiple IntelligentCommunications Managers (ICMs) 320, and with other ICP Platforms 200.Moreover, a single ICP Platform 200 may be distributed in multipleprocessors. The IFSS 313 provides the network interface required for allthese conditions.

The Accounting Subsystem (ACSS) 314 is responsible for collecting theTraffic Metering and Measurement (TMM) data and statistic messages fromsubsystems that generate these messages. The Recording Subsystem (RCSS)315 is responsible for collecting event and log messages for all othersubsystems. Event messages are accumulated over a short period of timewhile the events are buffered and duplicates are filtered out. Thevarious processes in the Data Management Subsystem (DMSS) 316 providefunctions for data storage and retrieval, data synchronization, datadistribution, data partition management, etc. Furthermore, the UtilitySubsystem (UTSS) 317 contains library routines that are developed forre-use by all subsystem processes.

The Intelligent Communication Manager (ICM) 320, a control andmanagement device, is connected via the TCP/IP link 330 to the ICPPlatform 200 for storage and display of logs, alerting, programmingcontrol policy rules, providing simple visibility, configuration, andother operational features of the ICP Platform 200. Multiple ICPPlatforms 200 can be managed by one ICM 320. Logs are routed via theTCP/IP link 330 from the ICP 200 to the ICM 320 and may range fromsimple events to full SS7 call or transaction messages. The TCP/IP link330 provides communication including, but not limited to, File TransferProtocol (FTP) Services and Internet Services between the ICP 200 andthe ICM 320.

The ICP Platform 200 has the capability to view data traversed on MTP2data links 14 and signaling units, except the Fill-in Signal Unit(FISU). In addition, the ICP Platform 200 can view all MSUs 300, i.e.,network management, traffic routing, test and upper layer protocols onMTP3 250 and can decode all Integrated Service Digital Network (ISDN)User Part (ISUP) messages and view all ISUP parameters and sub-fields.While not shown, it is understood that the ICP Platform 200 is can alsocommunicate within an enterprise network with various hosts forproviding management, configuration, and reporting functions.

The ICP Platform 200 is a fully active datalink layer (layer 2 of theseven layer Open Systems Interconnect (OSI) network model) device whileproviding layer three and above visibility and control. Network layercontrol messages, such as re-alignment messages, are transferredautonomously from node to node, e.g., from the SEP 210 to the SEP 220,within the SS7 network. The ICP Platform 200 manages these messages andcoordinates control between the end nodes 210/220. This allows end nodesto operate as masters of MTP2 240, while communicating directly to theICP Platform 200. MTP3 MSUs 300 are transferred end-to-end making theICP Platform 200 appear invisible to each SEP 210/220, at the networklayer and above.

The ICP Platform 200 is a full MTP2 signaling link terminal. It alsomanages MTP3 management messages between nodes 210 and 220.Additionally, it manages coordination of MTP3 traffic management, linkmanagement, and route management messages to synchronize MTP2 eventsbetween the two links. Functionally, the ICP Platform 200 consists ofSS7 I/O logic, which contains MTP1/MTP2 230/240, and MTP3 250 SS7stacks, located on the I/O card. The function of the stacks process MSUs300 for MTP3 250. Moreover, the ICP Platform 200 contains MTP3 controllogic located on the CPU card. These functions work independently ofeach other and provide a higher level visibility by processing signalingunits into MSUs 300 and MSUs into protocol data units (PDUs) (layer 4and above of the seven layer OSI network model).

FIG. 4 illustrates a functional diagram of the IntelligentCommunications Point (ICP) Platform 200. SS7 traffic 400 flows in andout the Signaling Subsystem 312 (SGSS) through the SS7 stack (MTP1/MTP2230/240 and MTP3 layer 250). SS7 messages are distributed to theprocesses in the Application Subsystem 270 (APSS). The APSS 270 sendsISUP messages to the SGSS 312 and in some cases the actions that itwants the SGSS 312 to carry out, such as start/stop sending MSU 300, andblock an SS7 message. In sum, the ICP Platform 200 combines call statemonitoring, line control, and transaction state control for implementingaccess and service control functions.

The ICP Platform 200 may be implemented with commercially availablecomponents as will be understood by those skilled in the art. While notshown, it is understood that the ICP Platform 200 is controlled bycomputer programming instructions stored in memory within the ICPPlatform 200 and potentially other components of the system connected tothe ICP Platform 200.

The Platform Control Subsystem (PCSS) 311 is responsible for themanagement of all other subsystems. PCSS 311 processes, which includethe Platform Control Process, the Rule Provisioning Process and the SS7Provisioning Process, have various responsibilities within the ICPPlatform 200. The Platform Control Process is ordinarily the firstprocess to start on the ICP Platform 200 and manages all other processesrunning on the ICP Platform 200. The Rule Provisioning Process managesthe process configuration profile and the application rule repository.This process receives updates from the IFSS 313 and makes updates to theDMSS 316. The SS7 Provisioning Process is responsible for SS7 Nodeprovisioning. This process will receive updates from the IFSS 313 andwill make updates to the SS7 stack, using vendor provided programminginterfaces.

The Signaling Subsystem (SGSS) 312, which is part of the core serviceslayer 260, contains the ISDN User Part (ISUP) process 410, the SignalingConnection Control Point (SCCP) process 420, the Signaling NetworkManagement 430 (SNM) and the Signaling Network Testing 430 (SNT). AllISUP process 410 and SCCP process 420 traffic can be processed through aSS7 firewall to enforce control policy rules. Management messages suchas re-alignment messages are controlled by the ICP Platform's 200control message manager application. Some of the common functionsprovided by the ISUP process 410, SCCP process 420 and SNM/SNT 430 areto generate events to report process start and stop and to reportabnormalities. In addition, they inform the MTP3 layer 250 of any statuschange so that traffic can be started or stopped.

The ISUP process 410 contained in the SGSS 312 is responsible forreceiving and forwarding ISUP messages between the MTP3 layer 250 andthe Application Layer 270. This process maintains connectivity to theApplication Layer 270 process and determines readiness of the ISUPmessage processing capability, and decodes and encodes the ISUP header.In addition, the ISUP process 410 distributes messages to theApplication Layer 270 processes, discards message response if timeoutoccurs, and takes default action if message response timeout occurs.

The SCCP process 420 is responsible for receiving and forwarding SCCPmessages between the MTP3 layer 250 and the Application Layer 270. TheSCCP process 420 provides communications between signaling nodes 210 and220 and provides specialized routing and management functions necessaryto support routing to partitioned and/or duplicate databases. Inaddition, this process returns messages back to MTP3 250 when message ischecked OK.

The SNM/SNT process 430 is responsible for receiving and forwardingSNM/SNT, and in particular the Link Status Signal Unit (LSSU) messagesand any other messages that the ISUP process 410 and SCCP 420 processcan not process. In addition, SNM/SNT process 430 generates TrafficMetering and Measurement (TMM) data and generates events to report LSSUdata.

The APSS 270 sends MSUs 300 to the ICM 320 through the InterfaceSubsystem 313 (IFSS). TMM data is generated by both the APSS 270 and theSGSS 312. Statistics are only generated by the APSS 270 and are sent tothe ICM 320 through the Accounting Subsystem 314 (ACSS). Every subsystemgenerates events and logs that are sent to the ICM 320 through theRecording Subsystem (RCSS) 315.

The ICM 320 provides configuration data for the ICP Platform 200 and theSS7 stack. As illustrated in FIG. 5, configuration data is sent to thePCSS 311 through the IFSS 313. The PCSS 311 updates the database withplatform configuration through the DMSS 316. SS7 node configuration issent to the UTSS 317. UTSS 317 interfaces with the SS7 stack (vendorsoftware portion) to change stack configuration. In addition, the ICM320 provides rules to the APSS 270 and SGSS 312, which use the rules todetermine message distribution and processing. Rules are first passed tothe Platform Control Subsystem 311 (PCSS) which updates the database atthe Data Management Subsystem 316 (DMSS). As illustrated in FIG. 6,rules are first passed from the IFSS 313 to the PCSS 311 which updatesthe database at the DMSS 316. The APSS 270 and the SGSS 312 then readthe rules as needed. The ICM 320 also sends the rule switching command(CMD) to the PCSS 311, which is processed and used in the same way asthe rules.

FIG. 7 illustrates SS7 traffic 400 distribution and supporting data flowin the system. SS7 traffic 400 flows in and out the SGSS 312. ISUP andMSU messages are distributed to the processes in the APSS 270. The APSS270 sends ISUP messages to the SGSS 312. The APSS 270 sends MSU datathrough the IFSS 313. TMM data is generated by both the APSS 270 and theSGSS 312 and is sent to the ICM 320 through the ACSS 314. Statistics aregenerated by the APSS 270 and are sent to the ICM 320 through the ACSS314. Every subsystem generates event and log data that are sent to theICM 320 through the RCSS 315.

It is understood that the present invention can take many forms andembodiments. The embodiments shown herein are intended to illustraterather than to limit the invention, it being appreciated that variationsmay be made without departing from the spirit of the scope of theinvention. The algorithms and process functions performed by the systemmay be organized into any number of different modules or computerprograms for operation on one or more processors or workstations withinthe system. Different configurations of computers and processors for thesystem are contemplated. The programs used to implement the methods andprocesses of the system may be implemented in any appropriateprogramming language and run in cooperation with any hardware device.The system may be used for service providers, Internet ServiceProviders, enterprises, and may other entities utilizing SS7 signalingdevices.

Although illustrative embodiments of the invention have been shown anddescribed, a wide range of modification, change and substitution isintended in the foregoing disclosure and in some instances some featuresof the present invention may be employed without a corresponding use ofthe other features. Accordingly, it is appropriate that the appendedclaims be construed broadly and in a manner consistent with the scope ofthe invention.

What is claimed is:
 1. Apparatus for intelligently redirecting datatraffic from a Public Switched Telephone Network (PSTN) to a datanetwork, the apparatus comprising: an intelligent communicationsplatform connected (ICP) between a switch and a Signaling System 7 (SS7)network to intercept SS7 messages between the switch and the SS7network; and a communications control module connected to the ICP via acommunication link, the communications control module for providingmanagement and communications to the ICP and providing access to themanagement and communication for a plurality of subscribers.
 2. Theapparatus of claim 1 wherein the ICP includes: an SS7 I/O card forprocessing SS7 messages; and a CPU card for processing ISUP and TCAP. 3.The apparatus of claim 1 wherein the communications control moduleincludes: instructions for communicating with other ICPs for updatedinformation on congestion on certain routes.
 4. The apparatus of claim 1wherein the communications control module includes: instructions for theplurality of subscribers to enter respective access line availability,alternative access numbers; and instructions for a plurality of users topopulate respective user profiles.
 5. The apparatus of claim 1 furtherincluding: an applications layer for hosting SS7 applications; a coreservices layer for providing a plurality of core services andinterconnected to the applications layer; an interface to the MessageTransfer Part layer 3 (MTP3) for receiving MTP3 messages andinterconnected to the core services layer; and an interface to theMessage Transfer Part layer 1 (MTP1) and the Message Transfer Part layer2 (MTP2) for receiving MTP1 and MTP2 messages and interconnected to theinterface to the MTP3.
 6. The apparatus of claim 5 wherein the interfaceto the MTP1/MTP2 includes at least two MTP1/MTP2 processors.
 7. Theapparatus of claim 5 wherein the core service layer supports a pluralityof support services and signaling processes to distribute traffic to theapplications layer and accept downward message routing requests.
 8. Theapparatus of claim 5 wherein the applications layer supports a pluralityof applications that monitor, modify or create messages.
 9. A method forintelligently redirecting data traffic from a Public Switched TelephoneNetwork (PSTN) to a data network, the method comprising: connecting anintelligent communications platform (ICP) to a switch and a SignalingSystem 7 (SS7) network to intercept SS7 messages between the switch andthe SS7 network; and connecting a communications control module to theICP via a communication link, the communications control module forproviding management and communications to the ICP and providing accessto the management and communication for a plurality of subscribers. 10.The method of claim 9 wherein further including: processing SS7 messagesat an SS7 I/O card within the ICP; and processing ISUP and TCAP messagesat a CPU card within the ICP.
 11. The method of claim 9 furtherincluding: communicating with other ICPs for updated information oncongestion on certain routes.
 12. The method of claim 9 furtherincluding: providing an interface for the plurality of subscribers toenter respective access line availability, alternative access numbers;and providing an interface for a plurality of users to populaterespective user profiles.
 13. The method of claim 9 further including:hosting SS7 applications on an applications layer; providing a pluralityof core services at a core services layer where the core services layeris interconnected to the applications layer; receiving MTP3 messages aninterface to the Message Transfer Part layer 3 (MTP3) where the MTP3 isinterconnected to the core services layer; and receiving MessageTransfer Part layer 1 (MTP1) and Message Transfer Part layer 2 (MTP2)messages at an interface to the MTP1 and the MTP2 where the interface tothe MTP1 and the MTP2 is interconnected to the interface to the MTP3.14. The method of claim 13 wherein the interface to the MTP1/MTP2includes at least two MTP1/MTP2 processors.
 15. The method of claim 13wherein the core service layer supports a plurality of support servicesand signaling processes to distribute traffic to the applications layerand accept downward message routing requests.
 16. The method of claim 13wherein the applications layer supports a plurality of applications thatmonitor, modify or create messages.
 17. Apparatus for intelligentlyredirecting data traffic from a Public Switched Telephone Network (PSTN)to a data network, the apparatus comprising: an intelligentcommunications platform connected (ICP) between a switch and a SignalingSystem 7 (SS7) network to intercept SS7 messages between the switch andthe SS7 network; a communications control module connected to the ICPvia a communication link, the communications control module forproviding management and communications to the ICP and providing accessto the management and communication for a plurality of subscribers; anSS7 I/O card for processing SS7 messages; a CPU card for processing ISUPand TCAP; an applications layer for hosting SS7 applications; a coreservices layer for providing a plurality of core services andinterconnected to the applications layer; an interface to the MessageTransfer Part layer 3 (MTP3) for receiving MTP3 messages andinterconnected to the core services layer; and an interface to theMessage Transfer Part layer 1 (MTP1) and the Message Transfer Part layer2 (MTP2) for receiving MTP1 and MTP2 messages and interconnected to theinterface to the MTP3.